Hi,
I have a project that's burried deep down in a folder/project tree and has access rights
Everyone else "R" and inherit from parent disabled. All its parent folders and projects have
access rights Everyone else "None". When I switch from the explorer module view ( where Everyone else
cannot see the project, or even it's parents ), to the project view .. voila .. I can see the projects and its modules
eg structure is : FolderA/FolderB/ProjectC/ProjectD/ModuleM
FolderA,FolderB,ProjectC have access rights GroupA "RMCD", Everyone else "None"
ProjectD,ModuleM have access rights GroupA "RMCD", Everyone else "R"
Is this a design feature or am I missing something here ?
Regards, Paul
SystemAdmin - Tue Aug 25 04:36:32 EDT 2009 |
Re: Seeing modules in Project View
llandale - Tue Aug 25 10:31:01 EDT 2009
Projects are both 'root' things and also 'nested' things. If you print the fullName("ModuleM") it will be "/ProjectD/ModuleM". There is also perm rootName_ that will give the full path back to the database root, "/FolderA/FolderB/ProjectC/ProjectD/ModuleM" in this case.
No two projects nor top-most folders can have the same name.
Even in database view, your DXL can still get at ProjectD and its modules and you can follow links to it.
If you have None access to a Project but Read access to one of its modules, you cannot actually load that module. Links to the module indicate 'ReadLocked', and trying to follow a link results in an ack error. That's good news for Project Admins, who can decide who cannot see anything in the Project and it cannot be overridden by Module Admins.
I really don't like nesting Projects as I cannot think of a realistic or theoretical reason for it. We do have top-level folders to house Projects of similar products.
|